-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix matchstick prediction issues #31418
base: master
Are you sure you want to change the base?
Fix matchstick prediction issues #31418
Conversation
Oh, I think you need to update yml of matches too... |
Your right but I have no idea why its failing... Isn't the default variable name lowercase? It was: |
Try removing read-only access, I don't know. |
Uh... The old one was read-only too... |
OK we couldn't figure out why it always fails when the datafield names are removed (Even when the names would still work...). Just leaving them there! |
|
||
// TODO make changes in icons when different threshold reached | ||
// e.g. different icons for 10% 50% 100% | ||
[RegisterComponent] | ||
public sealed partial class MatchboxComponent : Component | ||
{ | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs networking.
|
||
/// <summary> | ||
/// The time that the match will burn out. If null, that means the match is unlit. | ||
/// </summary> | ||
[AutoNetworkedField] | ||
public TimeSpan? TimeMatchWillBurnOut = null; | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs autopausedfield.
About the PR
Matchstick was always miss predicting getting inserted into a container. There was an outdated method that I fixed as well.
Technical details
The only sussy thing I had to do was always make the event handled if a matchstick is used on a matchbox. If you don't do that and check for it being lit and then making it list if its not, it starts misrepresenting on the second round because the match becomes lit and the event wouldn't be handled.
* This works the first time but the second time it will never trigger so it won't get handled and gets inserted.
Media
2024-08-24.22-39-04.mp4
Requirements